Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

After upgrade to ESXi 6.7 U2 and higher, vmkernel reports log spew with errors " Unmap6: 7146: [Unmap] <> Not supported (76827)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 10512Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

After the ESXi host is upgraded to ESXi 6.7 U2 or higher, vmkernel logs reports log spew with errors " Unmap6: 7146: [Unmap] <> Not supported.

In the vmkernel.log you will see entries similar to

2019-12-12T20:44:34.145Z cpu11:2134763)J6: 2651: 'Local104': Exiting async journal replay manager world

2019-12-12T20:45:29.148Z cpu21:2099111 opID=12dec6e3)World: 11943: VC opID sps-Main-641909-27-8f-5c-f0da maps to vmkernel opID 12dec6e3

2019-12-12T20:45:29.148Z cpu21:2099111 opID=12dec6e3)Unmap6: 7146: [Unmap] 'Local104':device(0x43059eabf110)does not support unmap

Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.

Purpose

To understand the cause of the log spew and to suppress the log spew.

Cause

A unmap function checks if the device supports unmap and if it does, it gets optimal unmap granularity and other properties of the device.

Impact / Risks

There is no impact of these errors as they are just informational messages logged in the vmkernel logs for the devices which do not support unmap.

Resolution

This issue is resolved in ESXi 6.7 P02 build 16075168 or higher.

Workaround

If upgrading is not possible then configure log rotation using the below commands
esxcli system syslog config set --default-rotate=30 --default-size=4096

esxcli system syslog reload

For more information refer to VMware KB : Configuring syslog on ESXi

The above settings helps to ensure that other critical logs are not being missed due to log spew.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vCenter Server を 6.5 U3 にアップグレードした後、LocalOS アカウントを使用して Windows セッション認証ログインを実行すると、無効な認証情報エラーで失敗する (76745)

KB
•
vSAN Health Service - 文件服务 - 基础架构运行状况 (76677)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

Take Our Survey

Support Assistant